feat: cargo-fuzz scaffolding for parser + solver + codegen (#138)#142
Merged
feat: cargo-fuzz scaffolding for parser + solver + codegen (#138)#142
Conversation
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
Adds `fuzz/` with three libfuzzer-sys harnesses and the CI plumbing to gate them: - `fuzz_aadl_parse` arbitrary bytes -> `spar_syntax::parse` - `fuzz_scheduler_solver` bounded `TaskSet` -> `solve_milp` - `fuzz_codegen_roundtrip` deterministic AADL + arbitrary knobs -> `generate` CI: - `fuzz-smoke` job in ci.yml runs 60s per target on PRs - `fuzz-nightly.yml` runs 1h per target daily at 03:00 UTC, caches and uploads corpus Traceability in `artifacts/verification.yaml`: `FUZZ-PARSER`, `FUZZ-SOLVER`, `FUZZ-CODEGEN` link to existing REQ-PARSE-*, REQ-PARSER-*, REQ-SOLVER-*, REQ-CODEGEN-* requirements. Closes #138. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
avrabe
force-pushed
the
fix/138-cargo-fuzz-targets
branch
2 times, most recently
from
f4ad049 to
e7f76d1
Compare
cargo-fuzz defaults to x86_64-unknown-linux-musl. musl's statically- linked libc is incompatible with ASan: sanitizer is incompatible with statically linked libc, disable it using `-C target-feature=-crt-static` Two fixes would work: (1) install musl + disable static libc via RUSTFLAGS, (2) pin --target x86_64-unknown-linux-gnu explicitly. Going with (2) — simpler and the CI runner has no need for musl's static-binary benefit. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
avrabe
force-pushed
the
fix/138-cargo-fuzz-targets
branch
from
e7f76d1 to
4d01931
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
fuzz/with three libfuzzer-sys targets: parser, solver, codegen-roundtripfuzz-smoke(60s/target on PRs) +fuzz-nightly.yml(1h/target daily, corpus cached)artifacts/verification.yamlTargets
fuzz_aadl_parsespar_syntax::parsefuzz_scheduler_solverspar_solver::milp::solve_milpfuzz_codegen_roundtripspar_codegen::generateCodegenConfigNotes
cargo fuzz buildwas not run locally (sandbox deniedcargo). Thefuzz-smokeCI job is the backstop.verifications:was the originally-spec'd YAML key; the file actually usesartifacts:— entries added under the existing key.FUZZ-PARSER,FUZZ-SOLVER,FUZZ-CODEGENlinking to the realREQ-*IDs found inartifacts/requirements.yaml.Test plan
fuzz-smokeCI job passes (compiles + 60s soak per target)rivet validateclean🤖 Generated with Claude Code